Yes, assuming the print files were created for Metacode or AFP printers. Here’s how:
Run the GenPrint program on the PC to generate an AFP print stream.
Allocate a sequential dataset with RECFM=VBM, LRECL=8205, BLKSIZE=23000.
Upload the AFP print stream (in binary) to the sequential dataset allocated in step 2.
Run the AFP2MVSX utility (look at sample in FSI.V102.JCLLIB) with the dataset in step 2 as input — in other words, put the dataset into DD:RSCOS2 in the AFP2MVSX JCL. This utility converts the AFP print stream from PC to MVS format and writes to the dataset specified by DD:RSCMVS in the AFP2MVSX JCL.
Run the GENERAFP job (see the sample in FSI.V102.JCLLIB) to send the MVS format AFP print stream from step 4 (the dataset in DD:RSCMVS) to the printer.
Generate the Metacode print stream on the PC in Xerox BARR format by including this INI option:
< PrtType:XER >
OutMode = BARR
Upload the print stream into an MVS data set with DCB characteristics. Here is an example:
DSORG: PS
RECFM: VBM
LRECL: 259 (higher is ok)
BLKSIZE: 23000 (high is ok)
Be sure your fonts and logos (as IMG or FNT files) are loaded on the Xerox printer. You might want to use a dataset name like:
FSI.V101.DMS1.GENPRINT.XERBAT1.FROMPC
Where FROMPC identifies the file as one that was uploaded into from the PC. Make sure you upload the dataset using binary mode. Otherwise, the print stream is converted from ASCII to EBCDIC. If you are using FTP, set the transfer mode to binary mode by specifying Binary.
Run the BARR2MVS utility to convert the print stream from BARR format to a format that the MVS and JES2 will be able to use. See the BARR2MVSX member in JCLLIB for sample JCL to run BARR2MVS. This job then...
Takes the uploaded dataset (such as FSI.V101.DMS1.GENPRINT.XERBAT1.FROMPC)
Removes the BARR information
Places the print-ready dataset into another dataset (such as FSI.V101.DMS1.GENPRINT.XERBAT1)
© Copyright 2017, Oracle and/or its affiliates. All rights reserved. Legal notices.